<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0039)http://www.dreamfabric.com/sms/pid.html -->
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<H1><A name=TP-PID></A>Protocol Identifier (TP-PID)</H1>The 
TP-Protocol-Identifier parameter consists of one octet, and the bits in the 
octet are used as follows: The MS will interpret reserved or unsupported values 
as the value 00000000 but shall store them exactly as received. The SC may 
reject messages with a TP-Protocol-Identifier containing a reserved value or one 
which is not supported. 
<BLOCKQUOTE>
  <TABLE width="90%" border=1>
    <TBODY>
    <TR bgColor=#ffffcc>
      <TD>Bit 7</TD>
      <TD>Bit 6</TD>
      <TD>Usage</TD></TR>
    <TR>
      <TD>0</TD>
      <TD>0</TD>
      <TD>Assigns bits 0..5 as defined below</TD></TR>
    <TR>
      <TD>0</TD>
      <TD>1</TD>
      <TD>Assigns bits 0..5 as defined below</TD></TR>
    <TR>
      <TD>1</TD>
      <TD>0</TD>
      <TD>Reserved</TD></TR>
    <TR>
      <TD>1</TD>
      <TD>1</TD>
      <TD>Assigns bits 0..5 for SC specific use</TD></TR></TBODY></TABLE>In case 
  where bits 7 and 6 both are 0: 
  <TABLE width="90%" border=1>
    <TBODY>
    <TR bgColor=#ffffcc>
      <TD>Bit 5</TD>
      <TD>Description</TD></TR>
    <TR>
      <TD>0</TD>
      <TD>no interworking, but SME-to-SME protocol</TD></TR>
    <TR>
      <TD>1</TD>
      <TD>telematic interworking</TD></TR></TBODY></TABLE>In the case of telematic 
  interworking, the following five bit patterns in bits 4..0 are used to 
  indicate types of telematic devices: 
  <TABLE width="90%" border=1>
    <TBODY>
    <TR bgColor=#ffffcc>
      <TD>Bits 4..0</TD>
      <TD>Description</TD></TR>
    <TR>
      <TD>00000</TD>
      <TD>implicit - device type is specific to this SC, or can be concluded 
        on the basis of the address</TD></TR>
    <TR>
      <TD>00001</TD>
      <TD>telex (or teletex reduced to telex format)</TD></TR>
    <TR>
      <TD>00010</TD>
      <TD>group 3 telefax</TD></TR>
    <TR>
      <TD>00011</TD>
      <TD>group 4 telefax</TD></TR>
    <TR>
      <TD>00100</TD>
      <TD>voice telephone (i.e. conversion to speech)</TD></TR>
    <TR>
      <TD>00101</TD>
      <TD>ERMES (European Radio Messaging System)</TD></TR>
    <TR>
      <TD>00110</TD>
      <TD>National Paging System (known to the SC)</TD></TR>
    <TR>
      <TD>00111</TD>
      <TD>Videotex (T.100/T.101)</TD></TR>
    <TR>
      <TD>01000</TD>
      <TD>teletex, carrier unspecified</TD></TR>
    <TR>
      <TD>01001</TD>
      <TD>teletex, in PSPDN</TD></TR>
    <TR>
      <TD>01010</TD>
      <TD>teletex, in CSPDN</TD></TR>
    <TR>
      <TD>01011</TD>
      <TD>teletex, in analog PSTN</TD></TR>
    <TR>
      <TD>01100</TD>
      <TD>teletex, in digital ISDN</TD></TR>
    <TR>
      <TD>01101</TD>
      <TD>UCI (Universal Computer Interface, ETSI DE/PS 3 01-3)</TD></TR>
    <TR>
      <TD>01110..<BR>..01111</TD>
      <TD>(reserved, 2 combinations)</TD></TR>
    <TR>
      <TD>10000</TD>
      <TD>a message handling facility (known to the SC)</TD></TR>
    <TR>
      <TD>10001</TD>
      <TD>any public X.400-based message handling system</TD></TR>
    <TR>
      <TD>10010</TD>
      <TD>Internet Electronic Mail</TD></TR>
    <TR>
      <TD>10011..<BR>..10111</TD>
      <TD>(reserved, 5 combinations)</TD></TR>
    <TR>
      <TD>11000..<BR>..11110</TD>
      <TD>values specific to each SC, usage based on mutual agreement between 
        the SME and the SC (7 combinations available for each SC)</TD></TR>
    <TR>
      <TD>11111</TD>
      <TD>A GSM mobile station. The SC converts the SM from the received 
        TP-DCS to any data coding scheme supported by that MS (e.g. the 
      default).</TD></TR></TBODY></TABLE>If bit 5 has value 1 in an SMS-SUBMIT PDU, 
  it indicates that the SME is a telematic device of a type which is indicated 
  in bits 4..0, and requests the SC to convert the SM into a form suited for 
  that device type. If the destination network is ISDN, the SC must also select 
  the proper service indicators for connecting to a device of that type. 
  <P>If bit 5 has value 1 in an SMS-DELIVER PDU, it indicates that the SME is a 
  telematic device of a type which is indicated in bits 4..0. 
  <P>If bit 5 has value 0 in an SMS-DELIVER PDU, the value in bits 4..0 
  indicates the SM-AL protocol being used between the SME and the MS. 
  <P>Note that for the straightforward case of simple MS-to-SC short message 
  transfer the Protocol Identifier is set to the value 0. 
  <P>In the case where bit 7 = 0, bit 6 = 1, bits 5..0 are used as defined below 

  <TABLE width="90%" border=1>
    <TBODY>
    <TR bgColor=#ffffcc>
      <TD>Bits 5..0</TD>
      <TD>Description</TD></TR>
    <TR>
      <TD>000000</TD>
      <TD>Short Message Type 0</TD></TR>
    <TR>
      <TD>000001</TD>
      <TD>Replace Short Message Type 1</TD></TR>
    <TR>
      <TD>000010</TD>
      <TD>Replace Short Message Type 2</TD></TR>
    <TR>
      <TD>000011</TD>
      <TD>Replace Short Message Type 3</TD></TR>
    <TR>
      <TD>000100</TD>
      <TD>Replace Short Message Type 4</TD></TR>
    <TR>
      <TD>000101</TD>
      <TD>Replace Short Message Type 5</TD></TR>
    <TR>
      <TD>000110</TD>
      <TD>Replace Short Message Type 6</TD></TR>
    <TR>
      <TD>000111</TD>
      <TD>Replace Short Message Type 7</TD></TR>
    <TR>
      <TD>001000..011110</TD>
      <TD>Reserved</TD></TR>
    <TR>
      <TD>011111</TD>
      <TD>Return Call Message</TD></TR>
    <TR>
      <TD>100000..111100</TD>
      <TD>Reserved</TD></TR>
    <TR>
      <TD>111101</TD>
      <TD>ME Data download</TD></TR>
    <TR>
      <TD>111110</TD>
      <TD>ME De-personalization Short MEssage</TD></TR>
    <TR>
      <TD>111111</TD>
      <TD>SIM Data download</TD></TR></TBODY></TABLE>
  <P>A short message type 0 indicates that the ME must acknowledge receipt of 
  the short message but may discard its contents. 
  <P>The Replace Short Message feature is optional for the ME and the SIM but if 
  implemented it shall be performed as descriped here. 
  <P>For MT short messages, on receipt of a short message from from the SC, the 
  MS shall check to see if the associated Protocol Identifier contains a Replace 
  Short Message Type code. 
  <P>If such a code is present, the the MS will check the originating address 
  and replace any existing stored message having the same Protocol Identifier 
  code and originating address with the new short message and other parameter 
  values. If there is no message to be replaced, the MS shall store the message 
  in the normal way. The MS may also check the SC address as well as the 
  Originating Address. However, in a network which has multiple SCs, it is 
  possible for a Replace Message type for a SM to be sent via different SCs and 
  so it is recommended that the SC address should not be checked by the MS 
  unless the application specifically requires such a check. 
  <P>If a Replace Short Message Type code is not present then the MS will will 
  store the message in the normal way. 
  <P>In MO short messages the SC reacts similarly but only the address of the 
  originating MS or any other source is checked. 
  <P>A Return Call Message indicates to the MS to inform the user that a call 
  (e.g. a telephone call) can be established to the address specified within the 
  TP-OA. The RP-OA contains the address of the SC as usual. The message content 
  (if present) gives displayable information (e.g. the number of waiting voice 
  messages). The message is handled in the same way as all other messages of the 
  Replace Short Message Types. 
  <P>The ME De-personalization Short Message is an ME-specific message which 
  instructs the ME to de-personalities the ME (see GSM 2.22). The TP-DCS shall 
  be set to Uncompressed, Default Alphabet, and Message Class 1 (Me-specific), 
  which corresponds to a bit coding og 00010001. The TP-UD field contains 
  de-personalization information coded according to GSM 02.22. This information 
  shall not be displayed by an ME which supports the scheme. The acknowledgement 
  to this message is a SMS-DELIVER-REPORT for RP-ACK in ehich the TP-User-Data 
  shall be coded according to GSM 02.22. 
  <P>SIM Data download is a facility whereby the ME must pass the short message 
  in its entirety including all SMS elements contained in the SMS deliver to the 
  SIM using the mechanism descriped in GSM 11.11. The DCS shall be set to 8 bit 
  message class 2 (either bit coding 11110110 or 00010110). The entire user data 
  field is available for SIM Data download. 
  <P>ME Data download is facility whereby the ME shall process the short message 
  in its entirety including all SMS elements contained in the SMS deliver to the 
  ME. The DCS shall be set to message class 1. The entire user data field is 
  available for ME data download. </P></BLOCKQUOTE></BODY></HTML>
